fix: cap DFS, add WINDOW clause and trailing comma support#24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WINDOWclause:SELECT ... WINDOW w AS (...)— supports multiple windows, inheritance (WINDOW w2 AS (w1 ROWS BETWEEN ...)), and inline/named mixing. Matches QuestDB's Java parser (feat(sql): window definition questdb#6746).SELECT a, b, FROM tnow parses cleanly, matching QuestDB runtime behavior.autocomplete-perf.test.ts).OVER wround-trip fix: named-window references were previously lost in the AST and serialized asOVER (). Now preserved end-to-end.WINDOWkeyword surfaces in autocomplete alongsideWINDOW JOINafter aFROMclause, so users can discover the new clause from the dropdown.